Agile Software Development Methodologies Research Articles

Design and Implementation of Computerized Restaurant Table Booking System

The dining landscape has transformed significantly with technological advancements, fundamentally altering how restaurants handle customer reservations. Traditionally, reservations were managed via phone calls or in-person visits, leading to issues like lengthy wait times, uncertain table availability, and limited communication channels. To address these challenges, this paper concentrates on crafting and implementing a Restaurant Table Booking System, aimed at streamlining reservations and enhancing customer experiences. Employing an agile software development methodology ensures flexibility, encourages customer input, and facilitates swift value delivery. Frontend development utilizes HTML, CSS, and Bootstrap for an intuitive user interface, while PHP and MySQL handle backend logic and database operations. Implementation emphasizes reliability and security through the Apache web server.

An Electrical Power Inventory and Monitoring System

The Inventory Management and Monitoring System is a software that is helpful for the various business sectors that operate in stores, products, and services where storeowners, products and services proprietors keep the records of sales and purchases, supply and demand, and risk and opportunities. A mismanaged inventory means disappointed customers, too much cash tied up in warehouses, slower sales, and sometimes detrimental to the work relation environment, investments and businesses, and most probably financial losses. Inventory control problems often result in record and physical count discrepancies which may ultimately lead to higher than preferred inventory levels. Conversely, accurate inventory records result in lower inventory investment and are the foundation for forecasting, ordering, tracking, vendor evaluation, dead stock, and administration plans and decisions.
 
 The researcher observed that most of the application of the inventory system was sales and products. Through this study, the researcher applied inventory in terms of electrical maintenance relations which includes electrical supplies, devices and equipment, services, and electrical power consumption. An Agile software development methodology was used in developing the system. The inventory archive maintenance system was developed using Java, HTML, CSS, PHP, PhpMyAdmin, and MySQL. The Inventory System includes Messaging, Supplies Inventory, Job Orders, Repair Records, and Wattage Consumption. Integration of disciplines made the study finished and the user’s manual was produced for guides and references for the use of the system.

Shedding light on the dark side – A systematic literature review of the issues in agile software development methodology use

ContextAgile software development (ASD) methodologies address problems of traditional approaches, but can also cause various issues. A systematization of the spectrum of negative facets and how they arise has not been developed, leaving the dark side of ASD opaque. ObjectiveThe paper systematizes findings on various negative facets to define what specific issues constitute the dark side of ASD. It also examines how relationships among these issues define the complexity of the downside. MethodA literature review of 70 articles was conducted following Kitchenham & Charters (2007). The content analysis employed the coding procedure by Gioia et al. (2013) to systematize the negative aspects of ASD methodologies. ResultsThe paper reveals 90 issues, grouped into 18 coherent themes. Six levels of manifestation point to the primarily affected constituents in ASD projects. In addition, 65 relationships among issues are explored, providing explanations for the complexity of the dark side of ASD. ConclusionThe systematization shows what aspects constitute the dark side of ASD, emphasizing its multidimensional nature along issues such as reduced developer well-being, product quality and development productivity. The analysis of how its complexity is defined reveals that customer misbehavior and delivery pressure are significant origins of other issues.

A Comparative Study of Agile and Waterfall Software Development Methodologies

In earlier software development all processes were completed and implemented but now this is not a scenario. In the modern era, changes are frequent to any software product or module that is in a development phase, due to market competition's priority of requirement changes Because the traditional process models are incompatible with these changes, agile methodology is used instead.. The earlier waterfall model was convenient because of less requirement of features and the emergency of the application in a short period. This Paper Discusses the Comparative Analysis of the waterfall model and agile methodologies while agile methodologies are taking over, even though the waterfall model is older and time-consuming it is still used in many sectors The paper will help other software development process models. The agile method plays an important role in the areas of software project management, software schedule management, etc. The main aim of agile is Customer satisfaction as well as faster development with a low defect rate. This reflects the comparison of the agile processes with the waterfall model software development life cycle model. Agile processes are always beneficial; they have their own set of downsides. The agile method promotes continuous iteration of development and testing throughout the software.

Analysis The Success of Knowledge Management in Agile Team Study Case: Ecommerce in Indonesia

Information in organizations needs to be managed to gain a competitive advantage in competitions. E-commerce, one of the most prominent industries in Indonesia, has dynamic market conditions that frequently change requirements and recent layoffs, which can harm the companies if not correctly managed. Knowledge and information usually stored in a knowledge management system (KMS) are essential to negate this, and Agile software development methodologies can manage frequent requirement changes. However, a study about KMS's success in Agile teams, primarily e-commerce, needs to be conducted to know if KMS can help companies sustain their business in Indonesia. This research analyses the KMS success in Indonesia's e-commerce companies that use Agile as their software development methodologies. This study used a quantitative approach with 31 respondents who worked or previously worked in an e-commerce company in Indonesia, using Agile as software development methodologies and experienced using KMS daily. Data was processed and analyzed using the Partial Least Square-Structural Equation Modeling (PLS-SEM) and SmartPLS tools. The results of this study indicate that KMS net benefits in Agile teams in E-commerce in Indonesia are influenced by the user's intentions to use and user satisfaction when using the KMS.

Critical Success Factors of Agile Software Development - A Systematic Literature Review

Agile software development has gained more popularity due to its capacity to manage constantly changing needs and generate high-quality software in less time. However, several success factors are required for an agile project to succeed. Agile development technique, delivery strategy, project team training, customer and staff involvement, management commitment, organizational culture, communication, and project management process are critical success factors (CSF) discovered in this study. This study's goal is to locate and evaluate these crucial elements of the agile software development methodology's success. A systematic literature review was conducted to study and analyze the previous studies to identify the CSFs in agile development. The findings of the literature review indicate that technical, people, organizational, and process factors are crucial for the success of agile projects. Each CSF falls into any one of these factors. Overall, this study's findings emphasize the significance of CSFs in the agile software development process. Organizations and software development teams can enhance their agile processes and raise the likelihood of project success by being aware of these aspects. Teams may create high-quality software in less time while simultaneously fulfilling the goals and expectations of the customer by concentrating on different success factors.

Critical success factors for DevOps adoption in information systems development

Adopting DevOps is challenging since it makes a significant paradigm shift in the Information Systems Development process. DevOps is a trending approach attached to the Agile Software Development Methodology, which facilitates adaptation to the customers' rapidly-changing requirements. It keeps one front step by introducing software operators who support the transmission between software and implementation into the software development team by confirming faster development, quality assurance, and easy maintenance of Information Systems (IS). However, software development companies reported challenges in adopting DevOps. It is critical to control those challenges while getting hold of the benefits by studying Critical Success Factors (CSF) for adopting DevOps. This study aimed to analyze the use of DevOps approach in IS developments by exploring CSFs of DevOps. A systematic literature review was applied to identify CSFs. These factors were confirmed by interviewing DevOps practitioners while identifying more frequent CSFs in the software development industry. Finally, the research presents a conceptual model for CSFs of DevOps, which is a guide to reap the DevOps benefits while reducing the hurdles for enhancing the success of IS. The conceptual model presents CSFs of DevOps by grouping them into four areas: collaborative culture, DevOps practices, proficient DevOps team, and metrics & measurement.

The Impact Of Remote Work On Organisational Climate Of Agile-Software Development Teams

Purpose: As a result of the changing labor market in a post-pandemic world, remote work in the IT sector is becoming almost a standard. It is known intuitively that the organisational climate changed compared to the stationary work, but it is difficult to determine how and what elements are going through the change. The aim of the article is to present the aspect of organisational climate in agile development teams working remotely compared to their stationary work. Methodology: The study was conducted using author own personally designed assessment questionnaire among ten programming teams using agile software development methodology. The number of members of the analysed teams varies from four to eight. This paper compares changes in each dimension of the organisational climate that have occurred in teams after switching to remote work. Using Cohen's d statistic, it determines the magnitude of the impact of these changes. Findings: The article is an attempt to answer which elements (dimensions) of the organisational climate, in what direction (positive vs negative) and to what extent (size effect) is remote work influencing in the context of agile software development teams. Value: Such knowledge will allow appropriate modeling of organisational climate factors, thus affecting performance and the well-being of team members. This is the first step to verify, whether the previous research about the impact of the organisational climate on agile development teams still applies to those teams working remotely.

Formal Methods for an Agile Scrum Software Development Methodology

Efficient, high-quality software systems embodying dependable methods are in high demand, which has led to a wide range of competitive market solutions. One effective technique that arguably has excelled above others is the Agile Software Development Methodology (ASDM). Agile approaches’ capacity to produce software in a way that is flexible to changes is the main factor that makes them preferable. Scrum, a recommended Agile methodology, prioritises feature coverage and project structure. Because iterative methodologies encourage engagement from cross-functional teams, including consumers, Agile provides flexibility in responding to change. However, achieving methodological efficiency is insufficient while developing software; high-quality software should be achieved with equal consideration. Formal Methods (FMs), which are mathematically based techniques, can offer highly dependable software but suffer from a steep learning curve in mastering the underlying discrete mathematics and logic. This research investigates the extent to which FMs may be embedded in traditional Agile as embodied by Scrum. Future work in this area would be the development of a framework for embedding FMs in Scrum, followed by a survey among software practitioners to establish the feasibility of our technique.

Risk management framework in Agile software development methodology

In software projects that use the Agile methodology, the focus is on development in small iterations to allow both frequent changes and client involvement. This methodology affects the risks that may happen in Agile software projects. Hence, these projects need a clear risk management process to reduce risks and address the problems before they arise. Most software production methodologies must use a framework for risk management, but currently, there is no such framework for the Agile methodology. Therefore, we present a risk management framework for projects that use the Agile methodology to help the software development process and increase the likelihood of the project’s success. The proposed framework states the necessary measures for risk management according to the ISO31000 standard at each stage of the Agile methodology. We evaluated the proposed framework in two running software projects with an Agile methodology by a number of expert experts. The results show that using our proposed framework increases the average positive risk reaction score by 49%.

Implementation of Agile Software Development Methodology in Software Projects

This research is a systematic literature review using Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) as a method to gather literature on agile software development methodology from Google Scholar. The result of this study is a summary of 11 articles related to Agile software development. The recommendation of this study is the use of the GLUX framework. GLUX framework integrates Lean UX into Scrum to improve the sustainability of the rapid software development process. It aims to promote a user-centric mindset and collaborative UX activities during the development process using gamification techniques. GLUX is about self-reliant teams, creating a motivating environment, and fostering teamwork.

Reporting in large-scale agile organizations: insights and recommendations from a case study in software development

Application of agile software development methodologies in large-scale organizations is becoming increasingly common. However, working with multiple teams and on multiple products at the same time yields higher coordination and communication efforts compared to single-team settings for which agile methodologies have been designed originally. With the introduction of agile methodologies at scale also comes the need to be able to report progress and performance not only of individual teams but also on higher aggregation of products and portfolios. Due to faster iterations, production of intermediate work results, increased autonomy of teams, and other novel characteristics, agile methodologies are challenging existing reporting approaches in large organizations. Based on 23 interviews with 17 practitioners from a large German car manufacturing company, this case study investigates challenges with reporting in large-scale agile settings. Further, based on insights from the case study, recommendations are derived. We find that combining reporting and agile methodologies in large-scale settings is indeed challenging in practice. Our research contributes to the understanding of these challenges, and points out opportunities for future research to improve reporting in large-scale agile organizations by goal-setting and automation.

Development of a web application for hotspot token vending machine administration

This article describes the features of a web application to manage the availability and acquisition of wireless internet access credentials of vending machine, it followed the OOHMD agile software development methodology, for the implementation we used the client-server architecture, the JavaScript programming language, the JavaScript runtime environment of Node. js JavaScript runtime environment, Express web development framework for Node.js, Sequelize ORM, MySQL relational database management system, Passport authentication middleware, EJS open source template engine, Bootstrap CSS framework, JSON data interchange format and Visual Studio Code IDE. As a contribution, there is a web application that allows the synchronization of available tokens and the sale of a wireless internet access credential vending machine, which connects through the internet. The methodology used allowed to have an adequate development process to obtain a quality product that resulted in a web application that efficiently provides the available access credentials and manages the access credentials acquired from the vending machine.

A Transgender Health Information Resource: Participatory Design Study

Background Despite the abundance of health information on the internet for people who identify as transgender and gender diverse (TGD), much of the content used is found on social media channels, requiring individuals to vet the information for relevance and quality. Objective We developed a prototype transgender health information resource (TGHIR) delivered via a mobile app to provide credible health and wellness information for people who are TGD. Methods We partnered with the TGD community and used a participatory design approach that included focus groups and co-design sessions to identify users’ needs and priorities. We used the Agile software development methodology to build the prototype. A medical librarian and physicians with expertise in transgender health curated a set of 97 information resources that constituted the foundational content of the prototype. To evaluate the prototype TGHIR app, we assessed the app with test users, using a single item from the System Usability Scale to assess feature usability, cognitive walk-throughs, and the user version of the Mobile Application Rating Scale to evaluate the app’s objective and subjective quality. Results A total of 13 people who identified as TGD or TGD allies rated their satisfaction with 9 of 10 (90%) app features as good to excellent, and 1 (10%) of the features—the ability to filter to narrow TGHIR resources—was rated as okay. The overall quality score on the user version of the Mobile Application Rating Scale was 4.25 out of 5 after 4 weeks of use, indicating a good-quality mobile app. The information subscore received the highest rating, at 4.75 out of 5. Conclusions Community partnership and participatory design were effective in the development of the TGHIR app, resulting in an information resource app with satisfactory features and overall high-quality ratings. Test users felt that the TGHIR app would be helpful for people who are TGD and their care partners.

A banking app for people with brain injuries: Co-designed by a person with aphasia and a speech and language therapist

We describe the process where a stroke survivor, his wife, and a speech language pathologist participated together to design and implement a new piece of software to help patients with brain injury recover skills needed to manage their finances. Each person provided a different perspective that led to a successful collaboration. The stroke survivor, a computer scientist, has experience with aphasia apps that he used in therapy. His wife, also a computer scientist, has experience with participatory design techniques and agile software development methodologies. The SLP understands the requirements needed for software to be useful for patients in a clinical setting. Together the team created an app that is currently being used in two rehab centers.

Bullet Id: A Virtual Bullet Identification for Forensic Ballistics Students

As school is a public place where the crowd is unavoidable and children are vulnerable, there is a need to strengthen policy in terms of the delivery of instruction - to provide opportunities for online learning platforms. Numerous innovative programs have been proposed by the different learning sectors in the Philippines. The Commission on Higher Education suggested strengthening online platforms and blended learning such as but not limited to google classroom, messenger, zoom, Edmodo, Facebook, and YouTube. This study was conducted using the Agile Software Development Methodology. The Bullet ID is a promising educational tool that will help both instructors and students in their learning activities, especially in the field of forensic ballistics. This new learning technology will bridge the gap between face-to-face and online classes. The main feature of this system is that it is an offline-based mobile application which made it different from the other forensic ballistic application developed by other researchers which are computer-based software application that requires an internet connection.

Web-based Management Information System of Cases Filed with National Labor Relations Commission

This study was developed to describe the daily operations and encountered problems of the National Labor Relations Commission Regional Arbitration Branch No. IV (NLRC RAB IV) through conducted observations and interviews. These problems were addressed and analyzed to be the features of the developed web-based management information system (MIS) for cases. The research methodology utilized in this project was the descriptive developmental approach. The Agile Software Development methodology was followed to develop the system. It was used to quickly produce the desired output while allowing the user to go back through phases without finishing the whole cycle. The system covered managing filed complaints, Single-Entry Approach (SEnA), labor cases, and report generation. The findings, through the interview, of handling records were inconsistent and inaccurate. This study also focused on ensuring the Data Privacy Act of 2012, protecting the database's information using the XOR Cipher Algorithm. This study was evaluated using standard web evaluation criteria. Using the criteria, the study's overall mean was 4.27 and 4.43, with the descriptive meaning of Very Good, which showed that the system was accepted as perceived by experts and end-users, respectively. Management of filed cases is a vital process for the Commission. With that said, developing a web-based management information system could ease the internal operations of handling and managing filed labor cases. Moreover, respondents and complainants can easily determine their filed cases' status using the case status tracking system. For further improvements to the system, additional printable documents may be added that could be found needed by the Commission. Lastly, further research about the effectiveness of the web-based system may be conducted for further enhancements of the system.

Web-based Database Courses E-Learning Application

This study was focused on the development of a web e-learning application for the database courses taken by Information Technology (IT) students at the College of Information and Communications Technology (CICT) of Bulacan State University (BulSU). The research methodology used in this project was the cross-sectional developmental approach. The Agile Software Development methodology was followed phase by phase, up to the development phase, to develop the system. It was used to produce the desired output rapidly while allowing users to go back through phases without finishing the whole cycle. The goal of this study was to create a web application that teaches Structured Query Language (SQL) in both the MySQL and SQL Server approaches. The application contains quizzes and examinations to allow self-assessment of learning. Additionally, an Entity Relationship Diagram (ERD) simulation was included to provide ERD creations in a drag-and-drop fashion. This study was evaluated using ISO/IEC 25010 software quality evaluation criteria. The study's overall mean was 4.24, 4.41, and 4.33, all with the descriptive meaning of "Very Good," which showed that the system performed its necessary functions as perceived by students, faculty members, and experts, respectively. In summary, the e-learning web application for database courses was fully developed. Moreover, the entity-relationship diagram was integrated well within the system and is accessible to the users. Lastly, respondents evaluated the developed web application using the ISO/IEC 25010 with an overall descriptive interpretation of "Very Good." For future developments of the study, an administrator panel may be developed to manage users and do other administrative tasks. Lastly, higher-order thinking skills questions on assessments and quizzes may be included.

Desarrollo de una herramienta computacional para evaluar la diversificación energética de los sistemas de transporte en Colombia

There is a growing demand for energy consumption in Colombia. For this rea-son, the country wants to promote poli-cies for the diversification of energy in its the transport systems. Thus, it is relevant to evaluate the energy and environmental impacts of promoting the increase of zero and low emission vehicles. The objective of this study is to show the development of a computational tool that implements seve-ral models and allows for the configuration of different technology scenarios to deter-mine the impact of the implementation of zero and low emission vehicle fleets. To develop the tool, an agile software deve-lopment methodology is used, which faci-litates following a systematic process for its construction. Using the computational tool, the user can obtain results for short-, medium-, and long-term projections.

Managing Critical Patient-Reported Outcome Measures in Oncology Settings: System Development and Retrospective Study.

Remote monitoring programs based on the collection of patient-reported outcome (PRO) data are being increasingly adopted in oncology practices. Although PROs are a great source of patient data, the management of critical PRO data is not discussed in detail in the literature. This first-of-its-kind study aimed to design, describe, and evaluate a closed-loop alerting and communication system focused on managing PRO-related alerts in cancer care. We designed and developed a novel solution using an agile software development methodology by incrementally building new capabilities. We evaluated these new features using participatory design and the Fit between Individuals, Task, and Technology framework. A total of 8 questionnaires were implemented using alerting features, resulting in an alert rate of 7.82% (36,838/470,841) with 13.28% (10,965/82,544) of the patients triggering at least one alert. Alerts were reviewed by 501 staff members spanning across 191 care teams. All the alerts were reviewed with a median response time of 1 hour (SD 185 hours) during standard business hours. The most severe (red) alerts were documented 56.83% (2592/4561) of the time, whereas unlabeled alerts were documented 27.68% (1298/4689) of the time, signaling clinician concordance with the alert thresholds. A PRO-based alert and communication system has some initial benefits in reviewing clinically meaningful PRO data in a reasonable amount of time. We have discussed key system design considerations, workflow integration, and the mitigation of potential impact on the burden of care teams. The introduction of a PRO-based alert and communication system provides a reliable mechanism for care teams to review and respond to patient symptoms quickly. The system was standardized across many different oncology settings, demonstrating system flexibility. Future studies should focus on formally evaluating system usability through qualitative methods.